feat: beacon chain and AVS fuzz tests #891
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8sunyuan
force-pushed
the
nadir/beacon-chain-and-avs-slashing-tests
branch
from
013b373
to
fcc1bec
Compare
8sunyuan
force-pushed
the
nadir/beacon-chain-and-avs-slashing-tests
branch
from
914c5c4
to
56774ab
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This test intends to demonstrate the composability of beacon chain and AVS slashing. In other words, performing a Beacon Chain slash against a staker, and then an AVS slash against a given operator, should yield the same outcome as the slashings occurring in the opposite order.
This test is a unit test to demonstrate the base proof-of-concept -- integration testing is a natural next step to bolster this assurance.